Empirical Analysis for Web Based Projects - Software Components Reuse Techniques

The basic connect of systematic software reuse is simple. Develop systems of components of a reasonable size and reuse them. Then extend the idea of component system beyond code alone to requirements, analysis models, design, and test. All the stages of the software development process are subject to reuse. Developers can save problemsolving effort all along the development chain. They can minimize redundant work. They can enhance the reliability of their work because each reused component system has already been reviewed and inspected in the course of its original development. Code components have passed unit and system test elsewhere and often have stood the test of use in the field. By these means developers can reduce development time from years to months, or to weeks instead of months. Keywords-Component, web engineering, azail [1] INTRODUCTION & RELATED WORK. The experience at companies such as AT & T, Brooklyn Union Gas, Ericsson, GTE, Hewlett-Packard, IBM, Motorola, NEC and Toshiba show that significant cost and time savings result from systematic reuse. Other companies, those that are doing nothing in particular about reuse, provide a base line. Several organizations have obtained reuse levels around 90% in certain projects or areas: AT & T: 40 – 92 % in Telecom operation support system software. Brooklyn Union Gas: 90 – 95 % in a process layer, and 67% in a user interface and business Object layer. Ericsson AXE: 90 % in hundreds of customer-specific configurations. Motorola: 85 % reuse and a 10: 1 productivity savings ratio in compiler and compiler-tool test Suites. Many organizations have achieved through reuse persuades us that management may expect substantial gains: Time to market: reductions of 2 to 5 times Defect density: reductions of 5 to 10 times Maintenance cost: reductions of 5 to 10 times Overall software development cost: reduction of around 15% to as much as 75% for long-term projects. Components are sometimes referred to as assets or work products. While the terms refer to the same underlying reality, they carry somewhat different connotations. Components suggests interfaces and packaging Asset brings to mind matters of ownership and management work product highlights the fact that a components is a unit in a cycle of work, the software life cycle. Revolution in application development: The growing popularity and availability of component-based software technologies is fueling a change in the habits and expectations of millions of programmers. New application development tools and technologies have made components the key to reusing larger grained objects to build application rapidly. These technologies include Micro Soft Visual Basic, ActiveX and OLE, SUN’s JAVA and CORBA interface definition language. Internet computing using applets and scripting languages such as VB Scripts and Java Scripts make it easy to develop and quickly deploy novel interactive applications across the enterprise. Component objects models and distributed computing infrastructure in the form of OMGs. CORBA middle ware technologies or Microsoft operating system support for the distributed components object model and OLE technology enable more complex distributed large-grain objects and components to e used. These technologies define and mange component interfaces separately from component implementations. Practical reuse has also been quite successful with nonobject-oriented languages such as COBAL and FORTRAN. These non-object-oriented components-based technologies reinter face the fact the successful reuse is not really about object oriented languages or class libraries. While object oriented languages have many of the qualities sought when developing components, they are not sufficient in themselves. There is a growing commercial market for components providing larger chunks of functionality than typical object classes do called ActiveX components or OLE components OCXs. As an increasing number of these component-based applications are constructed and deployed by independent developers. Business objects and components will be defined and constructed by separate groups, yet must work together to meet business information system needs. Vuppu Padmakar et al, / (IJCSIT) International Journal of Computer Science and Information Technologies, Vol. 5 (3) , 2014, 4398-4404